One way sound

ABSTRACT

A method and a system for identity authentication are presented. In one example embodiment, audio data (e.g. a sound wave) may be received from a user. The audio data may be used to establish an identity of an entity to the user. The audio data may be stored at a storage location; and be presented to the user to establish the identity of the entity when the entity participates in an electronic communication with the user. In another example embodiment, a server (e.g., a web client or client application server) may present a plurality of audio files to a user; receive a user selection of selected audio data from the plurality of audio files; responsive to the user selection, the server may communicate, via a network, the selected audio data to another server. The selected audio data may be used as an identity authentication.

PRIORITY

This application is a continuation of and claims the benefit of priorityunder to U.S. patent application Ser. No. 11/640,653, filed on Dec. 18,2006, which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present application relates generally to the technical field of dataauthentication and, in one specific example, to the use of audio datafor authentication of electronic communication.

BACKGROUND

For customers of businesses entities, such as Internet-based auctionfacilities, banks, and other financial institutions, when receiving anycommunication from the business, verification of the identity of thebusiness is particularly important for enhancing customer trust in thebusiness. Some financial institutions have started using images foridentity authentication. These institutions, typically, first ask eachof their customer to select an image from a group of images presented tothem via their web site. Then any time a user logs into their system toinitiate a transaction, the system presents the selected image toidentify the institute to the user, so that the user is confident anspoof website is not involved.

Therefore, it will be advantageous to provide user of various businessentities with the opportunity to verify the identity of specificbusiness entities from which they receive a call, text message or email.In particular, the users' confidence may be further augmented if theyare ask to provide the authentication tool, e.g. audio data to uniquelyidentify and validate the business that is trying to communicate withthem. For example, PAYPAL (a subsidiary of EBAY Inc., of San Jose,Calif.) now provides the users with a service which allows the user totransfer money using mobile phone. It will be particularly advantageousto provide the users of PAPAL, for example, a method to identify PAYPAL,using a customized audio data (e.g., a sound waves), when receiving aphone call from the company.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which:

FIG. 1 is a high level diagram depicting an example embodiment of anauthentication system;

FIG. 2 is a high level block diagram illustrating an example embodimentof a system for receiving authentication data and communicating to aserver;

FIG. 3 is a high-level block diagram illustrating an example embodimentof a network based server system;

FIG. 4 is a block diagram illustrating an example application server;

FIG. 5 is a block diagram illustrating an example embodiment of a systemfor receiving, storing and playing back audio data;

FIG. 6 is a block diagram illustrating an example embodiment of a systemfor receiving, storing and playing back sound waves;

FIG. 7 is a sequence diagram illustrating an example embodiment of amethod for receiving and storing audio data from a user;

FIG. 8 is a sequence diagram illustrating an example embodiment of amethod for receiving and storing audio data from a user;

FIG. 9 is a sequence diagram illustrating an example embodiment of amethod for receiving and storing audio data from a user;

FIG. 10 is a sequence diagram illustrating an example embodiment of amethod for authenticating a call from a messaging application to a userusing pre-stored audio data;

FIG. 11 is a sequence diagram illustrating an example embodiment of amethod for authenticating a call from an agent to a user usingpre-stored audio data;

FIG. 12 is a flow diagram illustrating an example embodiment of a methodfor receiving audio data and using the audio data for authenticating acommunication to a user;

FIG. 13 is a flow diagram illustrating an example embodiment of a methodfor receiving a selected audio data from a user and using the audio datafor authenticating a communication to the user; and

FIG. 14 is a block diagram illustrating a diagrammatic representation ofa machine in the example form of a computer system.

DETAILED DESCRIPTION

Example methods and systems to authenticate communication between asystem and its users using audio data are described. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of exampleembodiments. It will be evident, however, to one skilled in the art thatthe present invention may be practiced without these specific details.

A method and a system for authentication of electronic communicationbetween a system and its users are provided. In one example embodiment,a system (e.g., a network-based commerce system, a bank or any financialinstitution) may receive, audio data from a user, the audio data beingused to establish an identity of a first entity to the user; the systemmay store the audio data at a storage location (e.g. a file associatedwith the user stored on a storage device); and may present the audiodata to the user to establish an identity of the first entity when thefirst entity participates in an electronic communication with the user.In example embodiments, electronic communication may include text-basedcommunication (e.g., electronic mail (e-mail), instant message (IM),Short Message Service (SMS), facsimile), or audio communication over theInternet (e.g., Voice over IP (VoIP), or SKYPE, an Internet telephonyservice), or telephone call using wired Plain Old Telephone Service(POTS), or wireless networks (e.g., mobile, cellular, WiFi, and WiMAX).

In example embodiments, the storage location may be at a server systemremote from a client system of the user, and the presenting of the audiodata may include communicating the audio data from the server system tothe client system to establish the identity of the first entity. Also,presenting of the audio data may include generating an audio playbackthat is communicated to the user during the electronic communication.

The storage location may also be at a client system of the user, and themethod may include receiving a validation of the identity of the user atthe client system prior to the presenting of the audio data to the user.

In example embodiments, the first entity may be an agent of a businessentity (e.g., a network-based commerce system, a financial institutionsuch as a bank) electronically communicating with the user; the firstentity may be a machine (e.g. a computer based system) electronicallycommunicating with the user, on behalf of a business entity.

In one example embodiment, a user interface (e.g. a web page or a clientapplication) may present a plurality of audio data instances (e.g.pre-recorded sound waves) to a user; receive a user selection ofselected audio data from the plurality of audio data instances (e.g.,the user interface may present a plurality of sound waves to the user,so that the user may select a desired one from the presented soundwaves), the selected audio data (e.g. the user selected sound wave)being used as an identity authentication (e.g. to assure the user of theidentity of the system; the system may then, responsive to the userselection, communicate, via a network, the selected audio data to aserver.

The authentication of the communication between a system and its usersaugments the trust of the users in the system; and each time the systemtries to communicate with the user, it may provide them with confidencethat no spoof entity is involved. Indeed, both the system and the usersmay benefit from such authenticated communication.

System Architecture

FIG. 1 is a high level diagram depicting an example embodiment of anetworked authentication system 100. The system may include a networkedserver 140 communicating with a user 120 and a client system 110 (e.g. aweb client or a client application). The networked server 140 mayinclude a communication module 150 and a storage location 160.

In example embodiments, the communication module 150 may be acommunication server. The communication module may receive audio datafrom the user 120 and store that in the storage location 160 associatedwith the user 120. The communication module 150 may then retrieve thestored audio data from the storage location 160 and communicate theaudio data to the user to establish identity of the networked server140. The audio data may be generated from a sound wave (e.g. humanvoice) received from the user 120. The user 120 may be presented with aplurality of sound waves to select from. The networked server 140 thenmay store the selected sound wave as an audio data associated with theuser 120 in the storage location 160.

In one example embodiment, the receiving of the audio data from the user120 and storing the audio data at a storage location 160 may take placeat a first incidence of the first entity participating in an electroniccommunication with the user.

In one example embodiment, the receiving of the audio data from the user120 may include receiving a sound wave from the user 120, and convertingthe sound wave into the audio data. The receiving of the sound wave fromthe user 115 may constitute uploading a pre-recorded sound wave filefrom the client system 110, via the network 130, into a server site ofthe networked server 140.

In an example embodiment, the networked server 140 may use thecommunication module 150 to communicate, via a network 130 (e.g., theInternet), with a client system 110. The networked server 140 maypresent via a user interface in the client system 110 a plurality ofaudio data instances (e.g. sound waves) to a user 115 of the clientsystem 110. The user 115 may select a desired audio data from the audiodata instances provides by the networked server 140. The networkedserver 140 then may store the user selection in the storage location 160associated with the user 115. The networked server 140 may then retrievethe stored audio data and play back the audio data, to identify theowner of the networked server 140 (e.g. a business entity), to the user120 whenever a phone call is made or a text message or email is sent tothe user 120; or to the user 115 of the client system 110, whenever anycommunication with the user 115 is established, via the network 130,through client system 110. The networked server 140 may be the server ofa business entity, such as a network based commerce system, a bank, orany other financial or commercial institution.

In one example embodiment, the storage location may be located at aclient system 110 of the user, and the presenting of the audio data mayinclude receiving a validation of the identity of the first entity atthe client system 110.

FIG. 2 is a high level block diagram illustrating an example embodimentof a system 200 for receiving authentication data and communicating to aserver. The system 200 may include a subsystem 240 communicativelycoupled, via the network 130, with a networked server 140 and the user120, or the user 115 of the client system 110. The subsystem 240 mayinclude a receiver module 250 (hereinafter, “receiver”) and acommunication module 260.

In an example embodiment, the receiver 250 may receive audio data, viathe network 130, from the user 115 of the client system 110. Thecommunication module 260 then may communicate the audio data received bythe receiver 250, via the network 130, to the networked server 140. Theaudio data may then be used by the networked server 140 to establishidentification of the owner of the networked server 140 to a user of thenetworked server 140.

FIG. 3 is a high-level block diagram illustrating an example embodimentof a networked server system 300. A networked server 140 may provideserver-side functionality, via a network 130 (e.g., the Internet or WideArea Network (WAN)) to one or more clients. FIG. 3 illustrates, forexample, a web client 325 (e.g., a browser, such as the WINDOWS®INTERNET EXPLORER® browser developed by Microsoft Corporation ofRedmond, Wash. State), and a programmatic client 335 executing onrespective client machines 320 and 330.

An Application Program Interface (API) server 355 and a web server 365may be coupled to, and provide programmatic and web interfacesrespectively to, one or more applications server(s) 400. Theapplications server(s) 400 may host one or more server applicationsshown in FIG. 4. The applications server(s) 400 are, in turn, shown tobe coupled to one or more database server(s) 370 that facilitate accessto one or more database(s) 380.

Further, while the networked server 140 shown in FIG. 3 may employ aclient-server architecture, the present application is of course notlimited to such an architecture, and could equally well find applicationin a distributed, or peer-to-peer, architecture system, for example. Theweb client 325 may access the applications server(s) 400 via the webinterface supported by the web server 365. Similarly, the programmaticclient 335 may access the various services and functions provided by thenetworked server 140 and applications server(s) 400 via the programmaticinterface provided by the API server 355. The programmatic client 335may, for example, be a sound application to enable the networked server140 to retrieve a stored audio data from the storage location 160 andconvert it to a play back sound wave or to convert a sound wave receivedfrom a user to audio data to be stored in the storage location 160.

FIG. 4 is a block diagram illustrating an example application server400. The applications sever 400, may include a sound application 420, adispute resolution application 430, a messaging application(s) 440 and afraud prevention application 450. The applications may be hosted ondedicated or shared server machines (not shown) that are communicativelycoupled to enable communications between server machines. Theapplications themselves are communicatively coupled (e.g., viaappropriate interfaces) to each other and to various data sources, so asto allow information to be passed between the applications or so as toallow the applications to share and access common data. The applicationsmay furthermore access server one or more database(s) 380 via thedatabase server(s) 370.

Dispute resolution applications 430 may provide mechanisms wherebydisputes arising between transacting parties may be resolved. Forexample, the dispute resolution applications 430 may provide guidedprocedures whereby the parties are guided through a number of steps inan attempt to settle a dispute. In the event that the dispute cannot besettled via the guided procedures, the dispute may be escalated to athird entity mediator or arbitrator.

A number of fraud prevention applications 450 implement fraud detectionand prevention mechanisms to reduce the occurrence of fraud within thenetworked server 140.

Messaging application(s) 440 are responsible for the generation anddelivery of messages to users of the networked server 140, in theexample of a network based commerce system, such messages may be usedfor advising users regarding the status of listings at the networkedserver (e.g., providing “outbid” notices to bidders during an auctionprocess or to provide promotional and merchandising information tousers). Respective messaging application(s) 440 may utilize any one of anumber of message delivery networks and platforms to electronicallycommunicate with users to deliver messages to users.

Sound applications 420 may enable the networked server 140 to retrieve astored audio data from the storage location 160 and convert it to a playback sound wave or to convert a sound wave received from a user to audiodata to be stored in the storage location 160.

FIG. 5 is a block diagram illustrating an example embodiment of a system500 for receiving, storing and playing back audio data. The system 500may include a server 510 communicatively coupled to the user 120 and anagent computer 520. The server 510 may include a messaging application440, a communication module 560, the storage location 160, a soundplayer 550, and a sound recorder 580.

In one example embodiment, the agent 520 may try to use a messagingapplication 440 of the application server 400 to communicate with theuser 120. The agent 520 may initiate the communication automatically; ormay receive a instruction to that effect from a live agent who mayrepresent a business entity. In either case, the agent application maysend instructions to messaging application 440 to receive audio datafrom the user 120. The audio data to be used to identify the businessentity to the user 120, whenever the agent 520 or a live agentassociated with the business entity electronically communicates with theuser 120.

The messaging application 440 may arrange for the communication module560 to receive (e.g. by fetching a phone number from the storagelocation 160 and presenting it to that module and requesting that a callbe made to the user 120), an analog audio signal (e.g. a sound wave)from the user 120 or digital audio data from the mobile phone or a landline phone used by the user 120. The communication module 560 then maytransfer the received audio signal or data to a sound recorder 580,which may process the signal or data and convert it to a proper from(e.g. convert the analog signal to digital data after some amplificationand modification) for storage in the storage location 160 associatedwith the user 120.

In an example embodiment the server 510 may provide the user 120 with aplurality of audio data instances (e.g. sound waves) and ask the user120 to select a preferred audio data instance to be used to authenticatethe communication from the business entity.

Whenever an agent 520 tries to electronically communicate with the user120, the server 510 may play back the audio data or the sound waveassociated with the user 120 to the user 120. To perform the play back,the messaging application 440 may invoke the storage location 160 toretrieve the stored audio data associated with the user 120 and transferthe stored audio data to the sound player 550. The sound player 550 maythen process the transferred audio data (e.g. convert it to a properaudio signal ready to be communicated to the user 120) and pass it tothe communication module 560. The communication module 560 may thenplayback the audio signal to the user 120, during the call to the mobilephone or the land line phone used by the user 120. In an exampleembodiment, the playback may be invoked if it is requested by the user120.

FIG. 6 is a block diagram illustrating an example embodiment of a systemfor receiving, storing and playing back sound waves. In this exampleembodiment, the audio data to be used for authentication may be providedby the user 120 via a digital audio recorder 620 coupled to a personalcomputer 610 and communicated, via the network 130, to the server 650.

The server 650 may include a communication module 670, a messagingmodule 660, the storage location 160 and a controller module 690. Thecommunication module 670 may receive the audio data associated with theuser 120 from the network 130 and transfer it to the storage location160. Upon any phone call to the user 120 from the server 650, themessaging module 660 may authenticate the call by presenting the user120 with the stored audio data associated with the user 120 receivedfrom the storage location 160 The controller module 690 is coupled tothe communication module 670, the messaging module 660, and the storagelocation 160; and provide them with command and control signalsnecessary to coordinate the functions performed by above modules.

In example embodiments, the user 120 may use the digital audio recorder620 to record any preferred audio signal such as the user's voicereciting a specific text, singing a song, or making a special sound. Theuser 120 may also use an object (e.g. a musical instrument) to make theaudio signal.

Sequences Diagrams

FIG. 7 is a sequence diagram illustrating an example embodiment of amethod 700 for receiving and storing audio data from a user. Method 700may start by the user 115 of the client system 110 logging into thewebsite of a business entity hosted by the networked server 140(operation 720). The user 115 may then at operation 740 be presentedwith a plurality of audio data (e.g. sound waves) to select from. Theselected audio data (e.g. the preferred sound wave) at operation 750 maythen be stored in the storage location 160, associated with the user 115(operation 760). The stored audio data may be used for validation of theidentity of the business entity in future electronic communication ofthe business entity with the user 115.

FIG. 8 is a sequence diagram illustrating an example embodiment of amethod 800 for receiving and storing audio data from a user. The method800 starts with the user 115 of the client system 110 logging into thewebsite of a business entity hosted by the networked server 140(operation 820). The user 115 at operation 850 may provide an audio datainstance to the networked server 140. The networked server 140 then atoperation 860 may store the received audio data in the storage location160 associated with the user 115.

In example embodiments, the user 115 may use the digital audio recorder620 of FIG. 6 to record any preferred audio signal such as the user'svoice reciting a specific text, singing a song, or making a specialsound. The user 115 may also use an object (e.g. a musical instrument)to make the audio signal.

FIG. 9 is a sequence diagram illustrating an example embodiment of amethod 900 for receiving and storing audio data from a user. Accordingto the example method 900, an agent 520 of a business entity may invokethe messaging application 440 of the application server 400 to call theuser 120 and receive an audio data instance to be used to identify thebusiness entity, in future electronic communication with the user 120.The messaging application 440, at operation 940, may fetch the phonenumber of the user 120 from the storage location 160 and at operation950, the messaging application 440 may call the user 120. At operation960 the response to the call may be received from the user 120 by themessaging application 440. The messaging application 440 may atoperation 970 request the user 120 to provide an audio instance. Theaudio instance may be received, at operation 980, by the messagingapplication 440 from the user 120. At operation 990, the messagingapplication may store the received audio instance in the storagelocation 160 associated with the user 120.

In example embodiments, the calling of the user 120 by the messagingapplication 440, may include text-based communication (e.g., electronicmail (e-mail), instant message (IM), Short Message Service (SMS),facsimile), or audio communication over the Internet (e.g., Voice overIP (VoIP), or SKYPE, an Internet telephony service), or telephone callusing wired Plain Old Telephone Service (POTS), or wireless networks(e.g., mobile, cellular, WiFi, and WiMAX).

In example embodiments, the user 120 may use the digital audio recorder620 of FIG. 6 to record any preferred audio signal such as the user'svoice reciting a specific text, singing a song, or making a specialsound. The user 120 may also use an object (e.g. a musical instrument)to make the audio signal.

FIG. 10 is a sequence diagram illustrating an example embodiment of amethod for authenticating a call from a messaging application to a userusing pre-stored audio data. According to the example embodiment method1000, an agent 520 of a business entity may invoke the messagingapplication 440 of the application server 400 to call the user 120 andreceive an audio data instance to be used to identify the businessentity, in future electronic communication with the user 120. Themessaging application 440, at operation 1050, may fetch the phone numberof the user 120 from the storage location 160 and at operation 1060; themessaging application 440 may call the user 120. At operation 1070 theresponse to the call may be received from the user 120 by the messagingapplication 440. The messaging application 440 may at operation 1080fetch the audio data associated with the user 120 from the storagelocation 160. At operation 1090 the messaging application 440 mayplayback the audio data to the user 120, in order to authenticate thecall to the user 120.

In example embodiments, the agent 520 may be a live agent representingthe business entity (e.g., a financial institution, a networked basedcommerce system, etc.), or an agent computer system automaticallyinitiating calls to user 120.

In example embodiments, the calling of the user 120 by the agent 520,may include using text-based communication (e.g., electronic mail(e-mail), instant message (IM), Short Message Service (SMS), facsimile),or audio communication over the Internet (e.g., Voice over IP (VoIP), orSKYPE, an Internet telephony service), or telephone call using wiredPlain Old Telephone Service (POTS), or wireless networks (e.g., mobile,cellular, WiFi, and WiMAX).

FIG. 11 is a sequence diagram illustrating an example embodiment of amethod 1100 for authenticating a call from an agent to a user usingpre-stored audio data. According to the example embodiment method 1100,an agent 520 of a business entity may call the user 120 and receive anaudio data instance to be used to identify the business entity, infuture electronic communication with the user 120. The agent 520, atoperation 1140, may fetch the phone number of the user 120 from thestorage location 160 and at operation 1150; the agent 520 may call theuser 120. At operation 1160 the response to the call may be receivedfrom the user 120 by the agent 520. The agent 520 may at operation 1170fetch the audio data associated with the user 120 from the storagelocation 160. At operation 1180 the agent 520 may playback the audiodata to the user 120, in order to authenticate the call to the user 120.

In example embodiments, the agent 520 may be live agent representing thebusiness entity (e.g., a financial institution, a networked basedcommerce system, etc.) or an agent computer system automaticallyinitiating calls to user 120

In example embodiments, the calling of the user 120 by the messagingapplication 440, may include using text-based communication (e.g.,electronic mail (e-mail), instant message (IM), Short Message Service(SMS), facsimile), or audio communication over the Internet (e.g., Voiceover IP (VoIP), or SKYPE, an Internet telephony service), or telephonecall using wired Plain Old Telephone Service (POTS), or wirelessnetworks (e.g., mobile, cellular, WiFi, and WiMAX).

Flow Diagrams

FIG. 12 is a flow diagram illustrating an example embodiment of a method1200 for receiving audio data and using the audio data forauthenticating a communication to a user. The method 1200 starts atoperation 1210. At this operation the networked server 140, via thecommunication module 150 may receive an audio data instance from theuser 120 (see FIG. 1). AT operation 1220, the networked server 140 maystore the received audio data at the storage location 160. Thecommunication module 150 may retrieve the stored audio data from thestorage location 160 and present the retrieved audio data to the of theuser 120 or the user 115 of the client system 110, in future electroniccommunications with users 120 and 115 (operation 1230).

In example embodiments, the electronic communication with user 120 bythe messaging application 440, may include using text-basedcommunication (e.g., electronic mail (e-mail), instant message (IM),Short Message Service (SMS), facsimile), or audio communication over theInternet (e.g., Voice over IP (VoIP), or SKYPE, an Internet telephonyservice), or telephone call using wired Plain Old Telephone Service(POTS), or wireless networks (e.g., mobile, cellular, WiFi, and WiMAX).

FIG. 13 is a flow diagram illustrating an example embodiment of a method1300 for receiving a selected audio data from a user and using the audiodata for authenticating a communication to the user. According to theexample method 1300, the user 115 of the client system 110 may bepresented a plurality of audio data (operation 1310). The users may berequested to make a selection of the presented audio data. The receiver250 of the subsystem 240 (see FIG. 2) may then, at operation 1320,receive, via the network 130, the selected audio data from the clientsystem 110 and transfer it to the communication module 260. Thecommunication module 260 then may communicate, via the network 130, thereceived audio data to the networked server 140 (operation 1330. Theserver 140 may then store the audio data at storage location 160associated with the user 115. The stored audio data may then be playedback to the user 115 in future electronic communication with the user115 or user 120 (see FIG. 1).

Machine Architecture

FIG. 14 is a block diagram, illustrating a diagrammatic representationof machine 1400 in the example form of a computer system within which aset of instructions, for causing the machine to perform any one or moreof the methodologies discussed herein, may be executed. In alternativeembodiments, the machine may operate as a standalone device or may beconnected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a server computer, a client computer, a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a network router, switchor bridge, or any machine capable of executing a set of instructions(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while only a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein.

The example computer system 1400 may include a processor 1460 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 1470 and a static memory 1480, which communicate with eachother via a bus 1830. The computer system 1400 may further include avideo display unit 1410 (e.g., liquid crystal displays (LCD) or cathoderay tube (CRT)). The computer system 1400 also may include analphanumeric input device 1420 (e.g., a keyboard), a cursor controldevice 1430 (e.g., a mouse), a disk drive unit 1440, a signal generationdevice 1450 (e.g., a speaker) and a network interface device 1490.

The disk drive unit 1440 may include a machine-readable medium 1422 onwhich is stored one or more sets of instructions (e.g., software 1424)embodying any one or more of the methodologies or functions describedherein. The software 1424 may also reside, completely or at leastpartially, within the main memory 1470 and/or within the processor 1460during execution thereof by the computer system 1400, the main memory1470 and the processor 1460 also constituting machine-readable media.

The software 1424 may further be transmitted or received over a network426 via the network interface device 1490.

While the machine-readable medium 1422 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present invention. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories and optical and magnetic media.

Thus, a method and system to authenticate communication between a systemand a user have been described. Although the present invention has beendescribed with reference to specific example embodiments, it will beevident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope of theinvention. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

What is claimed is:
 1. A method comprising: establishing a firstelectronic networked communication between a client device of a user anda website hosted by an entity; receiving an audio data instance recordedby the user, from the client device, during the first electroniccommunication, the audio data instance being used to establish anidentity of the entity to the user; establishing, using one or moreprocessors, a second electronic communication between the user and theentity, the entity requesting communication with the user to establishthe second electronic communication; receiving a validation of theidentity of the user prior to the presenting the audio data instanceselected during the first electronic communication to the user; andpresenting the audio data instance selected during the first electroniccommunication to the user during the second electronic communication foridentity authentication in response to the user accepting the requestfrom the entity and participating in the second electronic communicationand in response to the received validation of the identity of the user.2. The method of claim 1, wherein the establishing the second electroniccommunication between the user and the entity includes establishing atelephone call between the entity and the user.
 3. The method of claim1, wherein the establishing the second electronic communication includesretrieving a phone number of the user from a database maintained by aserver.
 4. The method of claim 1, further comprising: storing the audiodata instance in a database maintained by a server, and wherein thepresenting the audio data instance to the user includes retrieving theaudio data instance from the database maintained by the server.
 5. Themethod of claim 1, wherein the second electronic communication betweenthe user and the entity includes a first device associated with the userand a second device associated with the entity.
 6. The method of claim5, wherein the presenting the audio data instance to the user during thesecond electronic communication includes sending the audio data instanceto the first device.
 7. The method of claim 1, wherein the firstelectronic communication includes at least one of: audio communicationover the Internet, Voice over IP, Plain Old Telephone Service, ortelephone call over wireless networks.
 8. The method of claim 1, furthercomprising: receiving a request to present the audio data instance, andwherein the presenting the audio data instance to the user is performedin response to receipt of the request.
 9. A system comprising: amessaging application, implemented using one or more processors, to:establish a first electronic networked communication between a clientdevice of a user and a website hosted by an entity; receive an audiodata instance recorded by the user, from the client device, during thefirst electronic communication, the audio data instance being used toestablish an identity of the entity to the user; establish a secondelectronic communication between the user and the entity, the entityrequesting communication with the user to establish the secondelectronic communication; receive a validation of the identity of theuser prior to the presenting the audio data instance selected during thefirst electronic communication to the user; and present the audio datainstance to the user during the second electronic communication foridentity authentication in response to the user accepting the requestfrom the entity and participating in the second electronic communicationand in response to the received validation of the identity of the user;and a sound recorder to store the audio data instance at a databasemaintained by a server.
 10. The system of claim 9, wherein the messagingapplication is further configured to establish a telephone call betweenthe entity and the user.
 11. The system of claim 9, wherein themessaging application is further configured to: retrieve a phone numberof the user from the database maintained by the server.
 12. The systemof claim 9, wherein the sound recorder is further configured to retrievethe audio data instance from the database maintained by the server. 13.The system of claim 9, wherein the second electronic communicationbetween the user and the entity includes a first device associated withthe user and a second device associated with the entity.
 14. The systemof claim 13, wherein the messaging application is further configured tosend the audio data instance to the first device.
 15. The system ofclaim 9, wherein the messaging application is further configured to:receive a request to present the audio data instance, and wherein thepresentation of the audio data instance to the user is performed inresponse to receipt of the request.
 16. A non-transitorymachine-readable medium storing instructions that, when executed by oneor more processors of a machine, cause the machine to perform operationscomprising: establishing a first electronic networked communicationbetween a client device of a user and a website hosted by an entity;receiving an audio data instance recorded by the user, from the clientdevice, during the first electronic communication, the audio datainstance being used to establish an identity of the entity to the user;establishing, using one or more processors, a second electroniccommunication between the user and the entity, the entity requestingcommunication with the user to establish the second electroniccommunication; receiving a validation of the identity of the user priorto the presenting the audio data instance selected during the firstelectronic communication to the user; and presenting the audio datainstance selected during the first electronic communication to the userduring the second electronic communication for identity authenticationin response to the user accepting the request from the entity andparticipating in the second electronic communication and in response tothe received validation of the identity of the user.